Why

• On the scheduled main canary, the OpenLineage e2e compat tests fail cause of image pull.
  • https://github.com/apache/airflow/actions/runs/29302223579
  • https://github.com/apache/airflow/actions/runs/29259909772
  • https://github.com/apache/airflow/actions/runs/29196225169
  • https://github.com/apache/airflow/actions/runs/29177468641
  • https://github.com/apache/airflow/actions/runs/29156049928
  • https://github.com/apache/airflow/actions/runs/29137134659
• The compat workflow builds the image openlineage-e2e/airflow:<version>-python<py> locally and never pushes it to a registry.

How

• Extend the no-pull prefix check in spin_up_airflow_environment to also cover the locally built openlineage-e2e/ tag.

Verification

• breeze testing airflow-e2e-tests --python 3.10 --e2e-test-mode openlineage --airflow-version 3.0.6

Was generative AI tooling used to co-author this PR?

• Yes - Claude Code

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.